I help product organizations build systems teams actually adopt.
Senior Product Designer specializing in Design Systems and DesignOps, with 7+ years of experience across organizations including Itaú Unibanco and Loft.
85%
Adoption in six months
22+
Brands
72+
Copan components
Philosophy
Most Design Systems don't fail from missing components, they fail from unclear ownership and governance nobody maintains.
A component library creates consistency. A Design System creates shared decision-making.
Experience highlights
Scale systems across organizations
22+ brands460+ designers5,000+ developers
Shared infrastructure designed for complex, multi-brand product organizations.
Align design and engineering
70% less handoff time60%+ faster component deliveryWCAG 2.1 library
Shared tokens, specifications and documentation reduced ambiguity between disciplines.
Enable adoption and governance
85% adoption40% community contribution5+ brands supported
Education, contribution pathways and continuous governance made adoption sustainable.
Every Design System solves a different organizational problem. Some improve consistency. Some reduce delivery friction. Others enable organizations to scale across multiple brands or hundreds of product teams. These projects focus not only on what was built, but on the decisions, trade-offs and organizational changes behind each system.
◆
[ {{ item.client }} ]{{ item.num }}
{{ item.title }}
{{ item.short }}
{{ tag }}
Trusted experience
Design systems shaped inside complex product organizations.
Itaú UnibancoLoftRede22+ brands across LATAM
How I work
01
Understand the organization
Every Design System reflects organizational decisions. Before defining components, I focus on understanding ownership, workflows, constraints and where inconsistency actually comes from.
02
Design the system
Architecture, tokens, documentation, governance and accessibility should work together. The goal isn't creating more assets, it's creating a system teams can confidently rely on.
03
Enable adoption
A Design System succeeds when people understand how and why to use it. Documentation, onboarding, education and collaboration are as important as the components themselves.
04
Measure impact
I measure success through adoption, consistency and delivery improvements, not by the number of components published.
Writing
5 min read · Jul 1, 2025
UX Is Folding Shirts Too: What a Year Behind the Counter Taught Me About Systems and Care.
Read article →
What colleagues say
{{ t.quote }}
{{ t.name }}
{{ t.role }}
About me
Beyond components. I design the systems that help organizations design better systems.
Throughout my career I've been less interested in creating interface libraries than understanding why organizations struggle to scale them.
As products grow, inconsistency rarely comes from missing components. It usually comes from fragmented decisions, unclear ownership, disconnected documentation and workflows that make collaboration difficult.
That's where my work begins.
Philosophy
Design Systems are operating models.
A Design System isn't simply a shared library. It's a product that supports other products. Its users aren't customers, they're designers, engineers and product teams making hundreds of decisions every day.
Because of that, successful systems require much more than good components. They require governance, documentation, accessibility, contribution models and continuous enablement.
How I think
I start with organizational problems.
Every Design System reflects how an organization works. Before creating components, I try to understand where inconsistency originates, which decisions repeat every sprint, and which problems are technical versus organizational, documentation should solve versus governance should solve. Only then does component design become meaningful.
Most Design Systems become difficult to maintain because organizations invest almost exclusively in the visible layer: components, libraries, tokens. The invisible layer, documentation, ownership, decision-making, education, contribution, versioning, adoption, usually receives less attention. Those areas have consistently been the focus of my work.
Building shared understanding across design, engineering, product, research, accessibility and leadership.
Working principles
Build less. Maintain better.
Adding components is easy. Removing complexity is harder. Whenever possible I prefer evolving existing patterns instead of expanding libraries.
Documentation is part of the product.
Documentation shouldn't explain the system. It should help people make decisions without needing the Design Systems team.
Governance should reduce friction.
Governance isn't approval. Good governance makes contribution safer while keeping delivery predictable.
Adoption matters more than publication.
Understanding why teams choose to use, or ignore, a Design System is often more valuable than publishing another release.
Experience
Loft
Product Designer, Design Systems & DesignOps
At Loft I helped build Copan, where the challenge shifted from scaling a design language to creating governance, contribution models and a Design System capable of supporting a rapidly growing multi-brand organization.
Proptech · BR
Itaú Unibanco
Product Designer, Design System & Ops
At Itaú Unibanco I worked on Design Systems and DesignOps at organizational scale, contributing to a white-label system supporting dozens of brands and thousands of product professionals. Across both experiences, the common thread wasn't component production, it was helping organizations make better product decisions together.
Banking · LATAM
I'm interested in organizations where Design Systems are treated as long-term infrastructure rather than short-term UI projects. Those environments create the most interesting design problems, because success depends as much on people and processes as it does on interfaces.
Let's build something solid.
Selected work
Systems, operations & products built to scale.
Ten projects across design systems, DesignOps, and digital product, from Itaú Unibanco, Loft, and Rede to a self-initiated retail concept.
[ Case-study copy, context, constraints, and the problem space. Adriana to drop the full narrative here. ]
[ PROCESS IMAGE ]
02 / Process
The approach
[ Research, decisions, artefacts, and the system/process you built. Add diagrams, screens and rationale. ]
03 / Outcome
The impact
[ Results, adoption, and what changed for the team and the business. ]
Next project
{{ active.nextTitle }}
→
Writing
Notes on systems, care & the craft of scaling design.
Featured · 5 min read · Jul 1, 2025
UX Is Folding Shirts Too: What a Year Behind the Counter Taught Me About Systems and Care.
On how a year of retail work reshaped the way I think about systems, repetition, and looking after the people who use what we build.
Read article →
Coming soon
Building contribution models that designers actually use
Coming soon
Accessibility as a default, not a checklist
Contact
Building something that needs to scale?
Whether you're evolving an existing Design System, creating one from scratch or improving collaboration between design and engineering, I'd love to hear about it.
